Dealbot #84
Dealbot #84
Conversation
ghost
ghost
changed the title
There was a problem hiding this comment.
I realized this got approved without as much review as many of our projects have. Left a comment to try to be more realistic about expected time since this seems clearly to need to be more solid than just some scripts, and to get stewards to weigh in on what's needed for sustainability.
|
|
||
|
|
||
| ## Project definition | ||
| #### Brief plan of attack |
There was a problem hiding this comment.
ℹ️ Noting that this project doesn't list
- Unit tests
- Monitoring of ongoing functionality of the bots
- Documentation for usage by external entities
With these, we should expect this project to be at least a 'medium' or to take at least 4 weeks of time.
There was a problem hiding this comment.
I'm 👍 on tests and docs.
For ongoing monitoring, the dashboards project might inadvertently solve for that. If the bots start failing, it will probably be immediately apparent to viewers of the dashboards (e.g., all metrics suddenly go to zero).
| - **Phase 2: Storage Bot.** Same idea but for storage deals. | ||
| - **Phase 3: Orchestrator.** Invokes the r-bot and s-bot programs with inputs one-by-one from a long queue of CIDs to test retrieve, or files to test store, etc. | ||
|
|
||
| #### What does done look like? |
There was a problem hiding this comment.
we do expect to be running this code for some time, and that is comes with both an infra and code burden.
Are there other criteria or thoughts that the stewards have for thinking about what they'd like to see before the project team moves on? cc @BigLep
mikeal
added
confidence:high
Initial proposal for storage and retrieval bots project.